Remove unnecessary logs while retrieving connections / variables#51786
Merged
amoghrajesh merged 3 commits intoapache:mainfrom Jun 17, 2025
Merged
Remove unnecessary logs while retrieving connections / variables#51786amoghrajesh merged 3 commits intoapache:mainfrom
amoghrajesh merged 3 commits intoapache:mainfrom
Conversation
jedcunningham
approved these changes
Jun 16, 2025
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
RoyLee1224
pushed a commit
to RoyLee1224/airflow
that referenced
this pull request
Jun 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When connection / secrets backend isnt setup, we should not log that those entities aren't found there.
It leads to wrong information and confusion.
DAG used:
No backend configured, logs show:
After fix:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.